[prod/HAFSv.2.2] Start HAFS v2.2 production branch#3164
[prod/HAFSv.2.2] Start HAFS v2.2 production branch#3164dpsarmie wants to merge 1 commit intoufs-community:production/HAFS.v2.2from
Conversation
|
I'll bring in other changes in a subsequent PR. This should be ready to merge into the HAFSv2.2 production branch. |
dpsarmie
requested review from
BrianCurtis-NOAA,
FernandoAndrade-NOAA,
NickSzapiro-NOAA,
gspetro-NOAA and
jkbk2004
|
Have these changes ever come into ufs-community before this? If not, maybe HAFS folks should review (too) |
|
Oops, should have added more detail in the description. HAFS has their own v2.2 branch that has been created and frozen for production but it lives on the hafs-community fork (https://github.com/hafs-community/ufs-weather-model/tree/production/hafs.v2.2). The last sync from HAFS to ufs-community was on Feb 10 and that's the base off of which the production branch was created here. The idea is to get all of those hafs-community production branches into the ufs-community fork (including all submodules). Most of these changes have been brought into develop. There are still some lingering fixes that are going to be synced (UFS-Utils and CCPP come to mind). I will make production branch PRs for those but we (UFSWM CMs) can talk to see if we hold those production branch merges until the changes get merged into develop. |
|
Maybe I'm confused but I find this hard to review It seems like the scotch module changes would break cpld_control_gfsv17 on some other platforms (like derecho and acorn). There should be a WW3 sub-component PR here too, no? And what is being tested? Ideally should RT baselines match between ufs-community and hafs-community branches? |
|
I can confirm that the WW3 branch is pointing to the HAFSv2.2 WW3 prod branch commit that I am expecting. |
3 participants
Commit Queue Requirements:
Description:
This PR is the beginning of the next few PRs to bring in a copy of the HAFS v2.2 production branch (https://github.com/hafs-community/ufs-weather-model/tree/production/hafs.v2.2) into the UFS WM repository. I created the HAFS v2.2 production branch from https://github.com/ufs-community/ufs-weather-model/tree/62b2c10d557b09656c728fdd339dfeb1c4e072d8 as the base. From there I will bring in the production branches across the different submodules until the UFSWM production branch matches the hafs-community production branch.
Commit Message:
Priority:
Git Tracking
UFSWM:
No issue for production branches
Sub component Pull Requests:
UFSWM Blocking Dependencies:
Documentation:
Changes
Regression Test Changes (Please commit test_changes.list):
Input data Changes:
Library Changes/Upgrades:
Testing Log: